<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
<html>
<head>
<!-- Copyright 1997 The Open Group, All Rights Reserved -->
<title>get</title>
</head><body bgcolor=white>
<center>
<font size=2>
The Single UNIX &reg; Specification, Version 2<br>
Copyright &copy; 1997 The Open Group

</font></center><hr size=2 noshade>
<h4><a name = "tag_001_014_833">&nbsp;</a>NAME</h4><blockquote>
get - get a version of an SCCS file (<b>DEVELOPMENT</b>)
</blockquote><h4><a name = "tag_001_014_834">&nbsp;</a>SYNOPSIS</h4><blockquote>
<pre><code>

get <b>[</b>-begkmlLpst<b>][</b>-c <i>cutoff</i><b>][</b>-i <i>list</i><b>][</b>-r <i>SID</i><b>][</b>-x <i>list</i><b>] </b><i>file</i>... 

get <b>[</b>-begkmpst<b>][</b>-c <i>cutoff</i><b>][</b>-i <i>list</i><b>][ </b>-l<b>[</b>p<b>]][</b>-r <i>SID</i><b>][</b>-x <i>list</i><b>]</b><i> file</i>... 
</code>
</pre>
</blockquote><h4><a name = "tag_001_014_835">&nbsp;</a>DESCRIPTION</h4><blockquote>
The
<i>get</i>
utility
generates a
text file from
each named SCCS
<i>file</i>
according to the specifications given
by its options.
<p>
The generated text is normally written into a file called the
<i>g-file</i>
whose name is derived from the SCCS filename by simply
removing the leading
<b>s.</b>.
<p>
</blockquote><h4><a name = "tag_001_014_836">&nbsp;</a>OPTIONS</h4><blockquote>
The
<i>get</i>
utility supports the <b>XBD</b> specification, <a href="../xbd/utilconv.html#usg"><b>Utility Syntax Guidelines</b>&nbsp;</a> ,
except that,
in the obsolescent form,
<b>-l</b>
option has an optional option-argument that
cannot be presented as a separate argument
(<b>-lp</b>).
When the
<b>-l</b>
and
<b>-p</b>
options are both needed,
the application must avoid ambiguity
by giving them as separate arguments
(<b>-l&nbsp;-p</b>),
reversing their sequence
(<b>-pl</b>)
or separating them with other options
in a single argument (such as
<b>-ltp</b>).
The following options are supported:
<dl compact>

<dt><b>-r&nbsp;</b><i>SID</i>
<dd>Indicate the SCCS Identification String (SID) of the version (delta)
of an SCCS file to be retrieved.
The table shows, for the most useful cases, what version
of an SCCS file is retrieved (as well as the SID
of the version to be eventually created by
<i><a href="delta.html">delta</a></i>
if the
<b>-e</b>
option is also used),
as a function of the SID specified.

<dt><b>-c&nbsp;</b><i>cutoff</i>
<dd>
Indicate the
<i>cutoff</i>
date-time, in the form:
<pre>
<code>
<i>YY</i><b>[</b><i>MM</i><b>[</b><i>DD</i><b>[</b><i>HH</i><b>[</b><i>MM</i><b>[</b><i>SS</i><b>]]]]]</b>
</code>
</pre>

For the <i>YY</i> component,
values in the range [69-99] refer to years in the twentieth century
(1969 to 1999 inclusive); values in the range [00-68] refer to
years in the twenty-first century (2000 to 2068 inclusive).

No changes (deltas) to the SCCS file that were created after
the specified
<i>cutoff</i>
date-time are included in the generated
text file.
Units omitted from the date-time default
to their maximum possible values;
for example,
<b>-c 7502</b>
is equivalent to
<b>-c 750228235959</b>.

Any number of non-numeric characters may separate
the various 2-digit pieces of the
<i>cutoff</i>
date-time.
This feature allows the user to specify a
<i>cutoff</i>
date in the form:
<b>-c "77/2/2 9:22:25"</b>.

<dt><b>-e</b>
<dd>Indicate that the
<i>get</i>
is for the purpose of editing or making a change
(delta) to the SCCS file via a subsequent use of
<i><a href="delta.html">delta</a></i>.
The
<b>-e</b>
option used in a
<i>get</i>
for a particular version (SID) of the SCCS file prevents
further
<i>get</i>
commands
from editing on the same SID until
<i><a href="delta.html">delta</a></i>
is executed or the
j
(joint edit) flag is set in the SCCS file.
Concurrent use of
<i>get</i>
<b>-e</b>
for different SIDs is always allowed.

If the
<i>g-file</i>
generated by
<i>get</i>
with a
<b>-e</b>
option is accidentally ruined in the process of editing,
it may be regenerated by reexecuting the
<i>get</i>
command with the
<b>-k</b>
option in place of the
<b>-e</b>
option.

SCCS
file protection specified via the
ceiling, floor and authorised user list
stored in the SCCS file is enforced when the
<b>-e</b>
option is used.

<dt><b>-b</b>
<dd>Use with the
<b>-e</b>
option to indicate that the new delta should have an SID in a new branch
as shown in the table below.
This option is ignored if the
b
flag is not present in the file
or if the retrieved delta is not a leaf delta.
(A leaf delta is one that has no successors on
the SCCS file tree.)
<dl><dt><b>Note:</b>
<dd>A branch delta may always be created from a non-leaf delta.
</dl>
<br>
<br>
<dt><b>-i&nbsp;</b><i>list</i>
<dd>Indicate a
<i>list</i>
of deltas to be included (forced to be applied)
in the creation of the generated file.
The
<i>list</i>
has the following syntax:
<pre>
<code>
&lt;list&gt; ::= &lt;range&gt; |  &lt;list&gt; , &lt;range&gt;
&lt;range&gt; ::= SID | SID - SID
</code>
</pre>
<p>
SID, the SCCS Identification of a delta, may
be in any form shown in the &quot;SID Specified&quot; column of
the table below.
Partial SIDs are interpreted as shown in the &quot;SID Retrieved&quot;
column of the table below.
<br>
<br>
<dt><b>-x&nbsp;</b><i>list</i>
<dd>Indicate a
<i>list</i>
of deltas to be excluded (forced not to be applied)
in the creation of the generated file.
See the
<b>-i</b>
option for the
<i>list</i>
format.
<br>
<dt><b>-k</b>
<dd>Suppress replacement of identification keywords
(see below) in the retrieved text by their value.
The
<b>-k</b>
option is implied by the
<b>-e</b>
option.
<br>
<dt><b>-l</b>
<dd>Write a delta summary into an
<i>l-file</i>.
<br>
<dt><b>-L</b>
<dd>Write a delta summary to standard output.
All informative output that normally is written to standard output
will be written to standard error instead, unless the
<b>-s</b>
option is used, in which case it is suppressed.
<br>
<dt><b>-lp</b>
<dd>Equivalent to
<b>-L</b>.
<br>
<dt><b>-p</b>
<dd>Write the text retrieved from the SCCS file to the standard output.
No
<i>g-file</i>
is created.
All informative output that normally goes to the standard output
goes to standard error instead,
unless the
<b>-s</b>
option is used, in which case it disappears.
<br>
<dt><b>-s</b>
<dd>Suppress all informative output normally written to standard output.
However, fatal error messages
(which are always written to the standard error)
remain unaffected.
<br>
<dt><b>-m</b>
<dd>Precede each text line retrieved from the SCCS file
by the SID
of the delta that inserted the text line in the SCCS file.
The format is:
<p><code>
<tt>"%s\ts"</tt>, &lt;<i>SID</i>&gt;,
&lt;<i>text&nbsp;line</i>&gt;
</code>
<br>
<br>
<dt><b>-n</b>
<dd>Precede each generated text line with the
<b>%M%</b>
identification keyword value (see below).
The format is:
<p><code>
<tt>"%s\ts"</tt>, &lt;<i>%M%&nbsp;value</i>&gt;,
&lt;<i>text&nbsp;line</i>&gt;
</code>
<p>
When both the
<b>-m</b>
and
<b>-n</b>
options are used, the
&lt;<i>text&nbsp;line</i>&gt;
is replaced by the
<b>-m</b>
option-generated format.
<br>
<br>
<dt><b>-g</b>
<dd>Suppress the actual retrieval of text from the SCCS file.
It is primarily used to generate an
<i>l-file</i>,
or to verify the existence of a particular SID.
<br>
<dt><b>-t</b>
<dd>Use to access the most recently created
(top) delta in a given release (for example,
r<b>-1</b>),
or release and level (for example,
r<b>-1.2</b>).
<p>
</dl>
</blockquote><h4><a name = "tag_001_014_837">&nbsp;</a>OPERANDS</h4><blockquote>
The following operands are supported:
<dl compact>

<dt><i>file</i><dd>A pathname of an existing SCCS file or a directory.
If
<i>file</i>
is a directory,
<i>get</i>
behaves as though each file in the directory were
specified as a named file,
except that non-SCCS files
(last component of the pathname does not begin with
s.)
and unreadable files are silently ignored.

If a single instance
<i>file</i>
is specified as -,
the standard input is read;
each line of the standard input is taken to be the name of an SCCS file
to be processed.
Non-SCCS files and unreadable files are silently ignored.

</dl>
</blockquote><h4><a name = "tag_001_014_838">&nbsp;</a>STDIN</h4><blockquote>
The standard input is a text file used only if the
<i>file</i>
operand is specified as -.
Each line of the text file is interpreted as an SCCS pathname.
</blockquote><h4><a name = "tag_001_014_839">&nbsp;</a>INPUT FILES</h4><blockquote>
The SCCS files are files of an unspecified format.
</blockquote><h4><a name = "tag_001_014_840">&nbsp;</a>ENVIRONMENT VARIABLES</h4><blockquote>
The following environment variables affect the execution of
<i>get</i>:
<dl compact>

<dt><i>LANG</i><dd>Provide a default value for the internationalisation variables
that are unset or null.
If
<i>LANG</i>
is unset or null, the corresponding value from the
implementation-dependent default locale will be used.
If any of the internationalisation variables contains an invalid setting, the
utility will behave as if none of the variables had been defined.

<dt><i>LC_ALL</i><dd>
If set to a non-empty string value,
override the values of all the other internationalisation variables.

<dt><i>LC_CTYPE</i><dd>
Determine the
locale for the interpretation of sequences of bytes of text data as
characters (for example, single- as opposed to multi-byte characters
in arguments and input files).

<dt><i>LC_MESSAGES</i><dd>
Determine the locale that should be used to affect
the format and contents of diagnostic
messages written to standard error,
and informative messages written to standard output
(or standard error, if the
<b>-p</b>
option is used).

<dt><i>NLSPATH</i><dd>
Determine the location of message catalogues
for the processing of
<i>LC_MESSAGES .
</i>
</dl>
</blockquote><h4><a name = "tag_001_014_841">&nbsp;</a>ASYNCHRONOUS EVENTS</h4><blockquote>
Default.
</blockquote><h4><a name = "tag_001_014_842">&nbsp;</a>STDOUT</h4><blockquote>
For each file processed,
<i>get</i>
writes to standard output the SID being accessed and
the number of lines retrieved from the SCCS file,
in the following format:
<p><code>
<tt>"%s\n%d lines\n"</tt>, &lt;<i>SID</i>&gt;,
&lt;<i>number&nbsp;of&nbsp;lines</i>&gt;
</code>
<p>
If the
<b>-e</b>
option is used, the SID of the delta to be made appears
after the SID
accessed and before the number of lines generated,
in the POSIX locale:
<p><code>
<pre>
<tt>"%s\nnew delta %s\n%d\n"</tt>, &lt;<i>SID&nbsp;accessed</i>&gt;,
&lt;<i>SID&nbsp;to&nbsp;be&nbsp;made</i>&gt;,
&lt;<i>number&nbsp;of&nbsp;lines</i>&gt;
</pre>
</code>
<p>
If there is more than one named file
or if a directory or standard input is named,
each pathname is written before each of the lines
shown in one of the preceding formats:
<p><code>
<tt>"\n%s:\n"</tt>, &lt;<i>pathname</i>&gt;
</code>
<p>
If the
<b>-L</b>
(or
<b>-lp</b>)
option is used, a delta summary will be written following
the format specified below for
<i>l-files</i>.
<p>
If the
<b>-i</b>
option is used, included deltas are listed following the notation,
in the POSIX locale:
<pre>
<code>
"Included:\n"
</code>
</pre>
<p>
If the
<b>-x</b>
option is used, excluded deltas are listed following the notation,
in the POSIX locale:
<pre>
<code>
"Excluded:\n"
</code>
</pre>
<p>
If the
<b>-p</b>,
<b>-L</b>
or
<b>-lp</b>
options are specified, the standard output consists of the
text retrieved from the SCCS file.
</blockquote><h4><a name = "tag_001_014_843">&nbsp;</a>STDERR</h4><blockquote>
The standard error is used only for diagnostic messages,
except if the
<b>-p</b>,
<b>-L</b>
or
<b>-lp</b>
options are specified, it includes all informative messages normally
sent to standard output.
</blockquote><h4><a name = "tag_001_014_844">&nbsp;</a>OUTPUT FILES</h4><blockquote>
Several auxiliary files may be created by
<i>get</i>.
These files are known generically as the
<i>g-file</i>,
<i>l-file</i>,
<i>p-file</i>
and
<i>z-file</i>.
The letter before the hyphen is called the
<i>tag .</i>
An auxiliary filename is formed from the SCCS file name:
the last component of
all SCCS filenames must be of the form
s.<i>module-name</i>
the auxiliary files are named by replacing the leading
s
with the tag.
The
<i>g-file</i>
is an exception to this scheme:
the
<i>g-file</i>
is named by removing the
s.
prefix.
For example, for
<b>s.xyz.c</b>,
the auxiliary filenames would be
<b>xyz.c</b>,
<b>l.xyz.c</b>,
<b>p.xyz.c</b>
and
<b>z.xyz.c</b>,
respectively.
<p>
The
<i>g-file</i>,
which contains the generated text,
is created in the current directory (unless the
<b>-p</b>
option is used).
A
<i>g-file</i>
is created in all cases, whether or not any lines of text
were generated by the
<i>get</i>.
It is owned by the real user.
If the
<b>-k</b>
option is used or implied, it is writable by the
owner only (read-only for everyone else);
otherwise it is read-only.
Only the real user need have
write permission in the current directory.
<p>
The
<i>l-file</i>
contains a table showing which deltas were applied
in generating the retrieved text.
The
<i>l-file</i>
is created in the current directory if the
<b>-l</b>
option is used;
it is read-only and it is owned by the real user.
Only the real user need have write permission in the
current directory.
<p>
Lines in the
<i>l-file</i>
have the following format:
<code>
<p>
<tt>"%c%c%c<img src="../images/delta.gif" border=0>%s\t%s<img src="../images/delta.gif" border=0>%s\n"</tt>, &lt;<i>code1</i>&gt;,
&lt;<i>code2</i>&gt;,
&lt;<i>code3</i>&gt;,
&lt;<i>SID</i>&gt;,
&lt;<i>date-time</i>&gt;,
&lt;<i>login</i>&gt;
</code>
</p>
<p>
where the entries are:
<dl compact>

<dt>&lt;<i>code1</i>&gt;<dd>A space character if the delta was applied;
"*" otherwise.

<dt>&lt;<i>code2</i>&gt;<dd>A space character if the delta was applied or was not applied and ignored;
"*" if the delta was not applied and was not ignored.

<dt>&lt;<i>code3</i>&gt;<dd>A character indicating a special reason
why the delta
was or was not applied:
<dl compact>

<dt><b>I</b><dd>Included.

<dt><b>X</b><dd>Excluded.

<dt><b>C</b><dd>Cut off (by a
<b>-c</b>
option).

</dl>
<p>
<dt>&lt;<i>date-time</i>&gt;<dd>
Date and time (using the
<i><a href="date.html">date</a></i>
utility's
%y/%m/%d%T
format)
of creation.
<p>
<dt>&lt;<i>login</i>&gt;<dd>Login name of person who created
<i><a href="delta.html">delta</a></i>.
<p>
</dl>
<p>
The comments and MR data follow on subsequent lines,
indented one tab character.
A blank line terminates each entry.
<p>
The
<i>p-file</i>
is used to pass information resulting from a
<i>get</i>
with a
<b>-e</b>
option along to
<i><a href="delta.html">delta</a></i>.
Its contents are also used to prevent a subsequent execution of
<i>get</i>
with a
<b>-e</b>
option for the same SID until
<i><a href="delta.html">delta</a></i>
is executed or the joint edit flag,
j,
is set in the SCCS file.
The
<i>p-file</i>
is created in the directory containing the SCCS file
and the effective user must have write permission in that directory.
It is writable by owner only, and it is owned by the effective user.
Each line in the
<i>p-file</i>
has the following format:
<code>
<p>
<tt>"%s<img src="../images/delta.gif" border=0>%s<img src="../images/delta.gif" border=0>%s<img src="../images/delta.gif" border=0>%s%s%s\n"</tt>, &lt;<i>g-file&nbsp;SID</i>&gt;,
&lt;<i>SID&nbsp;of&nbsp;new&nbsp;delta</i>&gt;,
&lt;<i>login-name&nbsp;of&nbsp;real&nbsp;user</i>&gt;,
&lt;<i>date-time</i>&gt;,
&lt;<i>i-value</i>&gt;,
&lt;<i>x-value</i>&gt;
</p>
</code>
<p>
where
&lt;<i>i-value</i>&gt;
uses the format &quot;&quot; if no <b>-i</b> option
was specified and uses the format:
<code>
<p>
<tt>"<img src="../images/delta.gif" border=0>-i%s"</tt>, &lt;<i>i option option-argument</i>&gt;
</p>
</code>
if a <b>-i</b> option was specified, and 
&lt;<i>x-value</i>&gt;
uses the format &quot;&quot; if no <b>-x</b> option was specified,
and uses the format:
<code>
<p>
<tt>"<img src="../images/delta.gif" border=0>-x%s"</tt>, &lt;<i>x option option-argument</i>&gt;
</p>
</code>
if a <b>-x</b> option was specified. 
There can be an arbitrary number of lines in the
<i>p-file</i>
at any time; no two lines can have the same new delta SID.
<p>
The
<i>z-file</i>
serves as a lock-out mechanism against simultaneous updates.
Its contents are the binary process ID of the
command (that is,
<i>get</i>)
that created it.
The
<i>z-file</i>
is created in the directory containing the SCCS file for the duration of
<i>get</i>.
The same protection restrictions as those for the
<i>p-file</i>
apply for the
<i>z-file</i>.
The
<i>z-file</i>
is created read-only.
<br>
</blockquote><h4><a name = "tag_001_014_845">&nbsp;</a>EXTENDED DESCRIPTION</h4><blockquote>
<pre>
<table  bordercolor=#000000 border=1 align=center><tr valign=top><th colspan=5 align=center><b>Determination of SCCS Identification String</b>
<tr valign=top><th align=center><b>SID*</b>
<th align=center><b>-b Keyletter</b>
<th align=center><b>Other</b>
<th align=center><b>SID</b>
<th align=center><b>SID of Delta</b>
<tr valign=top><th align=center><b>Specified</b>
<th align=center><b>Used</b>
<th align=center><b>Conditions</b>
<th align=center><b>Retrieved</b>
<th align=center><b>to be Created</b>
<tr valign=top><td align=left>none
<td align=center>no
<td align=center>R defaults to mR
<td align=left>mR.mL
<td align=left>mR.(mL+1)
<tr valign=top><td align=left>none
<td align=center>yes
<td align=center>R defaults to mR
<td align=left>mR.mL
<td align=left>mR.mL.(mB+1).1
<tr valign=top><td align=left>R
<td align=center>no
<td align=center>R &gt; mR
<td align=left>mR.mL
<td align=left>R.1***
<tr valign=top><td align=left>R
<td align=center>no
<td align=center>R = mR
<td align=left>mR.mL
<td align=left>mR.(mL+1)
<tr valign=top><td align=left>R
<td align=center>yes
<td align=center>R &gt; mR
<td align=left>mR.mL
<td align=left>mR.mL.(mB+1).1
<tr valign=top><td align=left>R
<td align=center>yes
<td align=center>R = mR
<td align=left>mR.mL
<td align=left>mR.mL.(mB+1).1
<tr valign=top><td align=left>R
<td align=center>-
<td align=center> R &lt; mR and R does not exist 
<td align=left>hR.mL**
<td align=left>hR.mL.(mB+1).1
<tr valign=top><td align=left>R
<td align=center>-
<td align=center> Trunk successor in release &gt; R and R exists 
<td align=left>R.mL
<td align=left>R.mL.(mB+1).1
<tr valign=top><td align=left>R.L
<td align=center>no
<td align=center>No trunk successor
<td align=left>R.L
<td align=left>R.(L+1)
<tr valign=top><td align=left>R.L
<td align=center>yes
<td align=center>No trunk successor
<td align=left>R.L
<td align=left>R.L.(mB+1).1
<tr valign=top><td align=left>R.L
<td align=center>-
<td align=center> Trunk successor in release &gt;= R 
<td align=left>R.L
<td align=left>R.L.(mB+1).1
<tr valign=top><td align=left>R.L.B
<td align=center>no
<td align=center>No branch successor
<td align=left>R.L.B.mS
<td align=left>R.L.B.(mS+1)
<tr valign=top><td align=left>R.L.B
<td align=center>yes
<td align=center>No branch successor
<td align=left>R.L.B.mS
<td align=left>R.L.(mB+1).1
<tr valign=top><td align=left>R.L.B.S
<td align=center>no
<td align=center>No branch successor
<td align=left>R.L.B.S
<td align=left>R.L.B.(S+1)
<tr valign=top><td align=left>R.L.B.S
<td align=center>yes
<td align=center>No branch successor
<td align=left>R.L.B.S
<td align=left>R.L.(mB+1).1
<tr valign=top><td align=left>R.L.B.S
<td align=center>-
<td align=center>Branch successor
<td align=left>R.L.B.S
<td align=left>R.L.(mB+1).1
</table>
</pre>
<dl compact>

<dt>*<dd>R, L, B and S are the release, level,
branch and sequence components of the SID, respectively;
m means maximum.
Thus, for example,
R.mL means &quot;the maximum level number within release R&quot;;
R.L.(mB+1).1 means &quot;the first sequence number on the
new branch (that is, maximum branch number plus
one) of level L within release R&quot;.
Note that if the SID specified is of the form R.L,
R.L.B or R.L.B.S, each of the specified components must exist.

<dt>**<dd>hR is the highest existing release that is lower than
the specified, non-existent, release R.

<dt>***<dd>This is used to force creation of the first
delta in a new release.

<dt><dd>The
<b>-b</b>
option is effective only if the
b
flag is present in the file.
An entry of - means &quot;irrelevant&quot;.


<dt><dd>This case applies if the
d
(default SID) flag is not present in the file.
If the
d
flag is present in the file, then the
SID obtained from the
d
flag is interpreted as if it had been specified on the command line.
Thus, one of the other cases in this table applies.

</dl>
<h5><a name = "tag_001_014_845_001">&nbsp;</a>Identification Keywords</h5>
Identifying information is inserted into the text retrieved from the
SCCS file by replacing identification keywords with their value
wherever they occur.
The following keywords may be used in the text stored in an SCCS file:
<dl compact>

<dt><b>%M%</b><dd>Module name: either the value of the
m
flag in the file, or if absent,
the name of the SCCS file with the leading
s.
removed.

<dt><b>%I%</b><dd>SCCS identification (SID)
(<i>%R%.%L%</i>
or
<i>%R%.%L%.%B%.%S%</i>)
of the retrieved text

<dt><b>%R%</b><dd>Release.

<dt><b>%L%</b><dd>Level.

<dt><b>%B%</b><dd>Branch.

<dt><b>%S%</b><dd>Sequence.

<dt><b>%D%</b><dd>Current date (<i>YY</i>/<i>MM</i>/<i>DD</i>).

<dt><b>%H%</b><dd>Current date (<i>MM</i>/<i>DD</i>/<i>YY</i>).

<dt><b>%T%</b><dd>Current time (<i>HH</i>:<i>MM</i>:<i>SS</i>).

<dt><b>%E%</b><dd>Date newest applied delta was created (<i>YY</i>/<i>MM</i>/<i>DD</i>).

<dt><b>%G%</b><dd>Date newest applied delta was created (<i>MM</i>/<i>DD</i>/<i>YY</i>).

<dt><b>%U%</b><dd>Time newest applied delta was created (<i>HH</i>:<i>MM</i>:<i>SS</i>).

<dt><b>%Y%</b><dd>Module type: value of the
t
flag in the SCCS file.

<dt><b>%F%</b><dd>SCCS filename.

<dt><b>%P%</b><dd>SCCS absolute pathname.

<dt><b>%Q%</b><dd>The value of the
q
flag in the file.

<dt><b>%C%</b><dd>Current line number.
This keyword is intended for identifying messages output by the
program, such as &quot;this should not have happened&quot; type errors.
It is not intended to be used on every line to provide
sequence numbers.

<dt><b>%Z%</b><dd>The four-character string
@(#)
recognisable by
<i><a href="what.html">what</a></i>.

<dt><b>%W%</b><dd>A shorthand notation for constructing
<i><a href="what.html">what</a></i>
strings:
<pre>
<code>
%W%=%Z%%M%&lt;tab&gt;%I%
</code>
</pre>

<dt><b>%A%</b><dd>Another shorthand notation for constructing
<i><a href="what.html">what</a></i>
strings:
<pre>
<code>
%A%=%Z%%Y%%M%%I%%Z%
</code>
</pre>

</dl>
</blockquote><h4><a name = "tag_001_014_846">&nbsp;</a>EXIT STATUS</h4><blockquote>
The following exit values are returned:
<dl compact>

<dt>0<dd>Successful completion.

<dt>&gt;0<dd>An error occurred.

</dl>
</blockquote><h4><a name = "tag_001_014_847">&nbsp;</a>CONSEQUENCES OF ERRORS</h4><blockquote>
Default.
</blockquote><h4><a name = "tag_001_014_848">&nbsp;</a>APPLICATION USAGE</h4><blockquote>
None.
</blockquote><h4><a name = "tag_001_014_849">&nbsp;</a>EXAMPLES</h4><blockquote>
None.
</blockquote><h4><a name = "tag_001_014_850">&nbsp;</a>FUTURE DIRECTIONS</h4><blockquote>
The
<b>-lp</b>
option may be withdrawn in a future issue.
</blockquote><h4><a name = "tag_001_014_851">&nbsp;</a>SEE ALSO</h4><blockquote>
<i><a href="admin.html">admin</a></i>,
<i><a href="delta.html">delta</a></i>,
<i><a href="prs.html">prs</a></i>,
<i><a href="what.html">what</a></i>.
</blockquote><hr size=2 noshade>
<center><font size=2>
UNIX &reg; is a registered Trademark of The Open Group.<br>
Copyright &copy; 1997 The Open Group
<br> [ <a href="../index.html">Main Index</a> | <a href="../xshix.html">XSH</a> | <a href="../xcuix.html">XCU</a> | <a href="../xbdix.html">XBD</a> | <a href="../cursesix.html">XCURSES</a> | <a href="../xnsix.html">XNS</a> ]

</font></center><hr size=2 noshade>
</body></html>
